runtime: avoid zeroing scavenged memory #76063

ioworker0 · 2025-10-27T05:08:48Z

On Linux, memory returned to the kernel via MADV_DONTNEED is guaranteed
to be zero-filled on its next use.

This commit leverages this kernel behavior to avoid a redundant software
zeroing pass in the runtime, improving performance.

gopherbot · 2025-10-27T05:15:11Z

This PR (HEAD: 5b2d4a4) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/715160.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-10-27T05:23:35Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T05:31:45Z

Message from Lance Yang:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T05:39:52Z

Message from t hepudds:

Patch Set 1: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T05:47:57Z

Message from Go LUCI:

Patch Set 1:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-10-27T05:29:16Z","revision":"9a51fbcf842017a87bfcb3b8eec08caa7f2b3b42"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T05:47:58Z

Message from t hepudds:

Patch Set 1: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T05:47:58Z

Message from Go LUCI:

Patch Set 1:

This CL has failed the run. Reason:

Tryjob golang/try/x_debug-gotip-linux-amd64 has failed with summary (view all results):

go on master (change 715160) / debug on master (commit 6760acc)

To reproduce, try gomote repro 8699882044559958929.

Additional links for debugging:

make.bash output

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T05:47:59Z

Message from Go LUCI:

Patch Set 1: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T05:56:13Z

This PR (HEAD: 6cde005) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/715160.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-10-27T06:04:28Z

Message from Lance Yang:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T09:36:48Z

Message from Jorropo:

Patch Set 2: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T09:45:16Z

Message from Go LUCI:

Patch Set 2:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-10-27T09:29:54Z","revision":"2174f04568be29dc18b4eff3b779f14bb0579f69"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T09:53:42Z

Message from Jorropo:

Patch Set 2: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T09:53:43Z

Message from Go LUCI:

Patch Set 2:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-linux-amd64_avx512-greenteagc has failed with summary (view all results):

go on master (change 715160)

To reproduce, try gomote repro 8699866901202967905.

Additional links for debugging:

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T09:53:43Z

Message from Go LUCI:

Patch Set 2: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T10:56:34Z

This PR (HEAD: 38d7ab8) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/715160.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-10-27T11:19:20Z

Message from Jorropo:

Patch Set 3: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T11:28:45Z

Message from Go LUCI:

Patch Set 3:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-10-27T11:12:21Z","revision":"d2d4f8243afaf5940be99dd69749fcc7629706a8"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T11:37:51Z

Message from Jorropo:

Patch Set 3: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T11:37:51Z

Message from Go LUCI:

Patch Set 3:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-linux-amd64_avx512-greenteagc has failed with summary (view all results):

go on master (change 715160)

To reproduce, try gomote repro 8699860457172895089.

Additional links for debugging:

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T11:37:52Z

Message from Go LUCI:

Patch Set 3: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T11:55:24Z

This PR (HEAD: 526ce3d) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/715160.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-10-27T12:04:08Z

Message from Lance Yang:

Patch Set 4:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T12:13:09Z

Message from t hepudds:

Patch Set 4: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T12:13:10Z

Message from Go LUCI:

Patch Set 4:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-10-27T12:00:40Z","revision":"fb86fc61e95b33671f4770d49d85f23c1d51bcc5"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T12:31:01Z

Message from t hepudds:

Patch Set 4: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T12:31:01Z

Message from Go LUCI:

Patch Set 4:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T16:20:54Z

This PR (HEAD: 438c095) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/715160.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-10-27T16:37:59Z

Message from t hepudds:

Patch Set 5: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T16:46:05Z

Message from Go LUCI:

Patch Set 5:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-10-27T16:27:27Z","revision":"6fb2b26354d1f304d427f0464fccc2b9a5181919"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T16:46:06Z

Message from t hepudds:

Patch Set 5: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T16:46:06Z

Message from Go LUCI:

Patch Set 5:

This CL has failed the run. Reason:

Tryjob golang/try/x_debug-gotip-linux-amd64 has failed with summary (view all results):

go on master (change 715160) / debug on master (commit 6760acc)

To reproduce, try gomote repro 8699840632314708225.

Additional links for debugging:

make.bash output

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-27T16:46:07Z

Message from Go LUCI:

Patch Set 5: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-28T02:37:39Z

This PR (HEAD: fefae7f) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/715160.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-10-28T03:33:33Z

This PR (HEAD: 46fae8d) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/715160.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-10-28T04:52:07Z

This PR (HEAD: 439a33e) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/715160.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-10-28T05:52:16Z

Message from Lance Yang:

Patch Set 8:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

On Linux, memory returned to the kernel via MADV_DONTNEED is guaranteed to be zero-filled on its next use. This commit leverages this kernel behavior to avoid a redundant software zeroing pass in the runtime, improving performance. Signed-off-by: Lance Yang <[email protected]>

gopherbot · 2025-10-28T08:02:19Z

This PR (HEAD: 6c8df32) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/715160.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-10-28T08:10:36Z

Message from Lance Yang:

Patch Set 8:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-28T09:43:04Z

Message from t hepudds:

Patch Set 9: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-28T09:43:04Z

Message from Go LUCI:

Patch Set 9:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-10-28T09:33:31Z","revision":"fbff89c8ffbd0b4747e1f68b1007f496f458c413"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-28T10:08:12Z

Message from t hepudds:

Patch Set 9: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-28T10:08:13Z

Message from Go LUCI:

Patch Set 9:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-28T10:08:14Z

Message from Go LUCI:

Patch Set 9: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-28T15:59:53Z

Message from Lance Yang:

Patch Set 9:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-28T20:48:46Z

Message from Michael Knyszek:

Patch Set 9: Code-Review+2

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-28T20:48:47Z

Message from Michael Knyszek:

Patch Set 9:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-10-29T14:34:43Z

Message from David Chase:

Patch Set 9: Code-Review+2

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/715160.
After addressing review feedback, remember to publish your drafts!

On Linux, memory returned to the kernel via MADV_DONTNEED is guaranteed to be zero-filled on its next use. This commit leverages this kernel behavior to avoid a redundant software zeroing pass in the runtime, improving performance. Change-Id: Ia14343b447a2cec7af87644fe8050e23e983c787 GitHub-Last-Rev: 6c8df32 GitHub-Pull-Request: #76063 Reviewed-on: https://go-review.googlesource.com/c/go/+/715160 LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Michael Knyszek <[email protected]> Reviewed-by: David Chase <[email protected]>

gopherbot · 2025-10-31T12:43:27Z

This PR is being closed because golang.org/cl/715160 has been merged.

ioworker0 force-pushed the master branch from 5b2d4a4 to 6cde005 Compare October 27, 2025 05:53

ioworker0 force-pushed the master branch from 6cde005 to 38d7ab8 Compare October 27, 2025 10:55

ioworker0 force-pushed the master branch from 38d7ab8 to 526ce3d Compare October 27, 2025 11:52

ioworker0 force-pushed the master branch from 526ce3d to 438c095 Compare October 27, 2025 16:17

ioworker0 force-pushed the master branch from 438c095 to fefae7f Compare October 28, 2025 02:36

ioworker0 force-pushed the master branch from fefae7f to 46fae8d Compare October 28, 2025 03:29

ioworker0 force-pushed the master branch from 46fae8d to 439a33e Compare October 28, 2025 04:47

ioworker0 force-pushed the master branch from 439a33e to 6c8df32 Compare October 28, 2025 07:57

gopherbot closed this Oct 31, 2025

runtime: avoid zeroing scavenged memory #76063

runtime: avoid zeroing scavenged memory #76063

Conversation

ioworker0 commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 27, 2025

Uh oh!

gopherbot commented Oct 28, 2025

Uh oh!

gopherbot commented Oct 28, 2025

Uh oh!

gopherbot commented Oct 28, 2025

Uh oh!

gopherbot commented Oct 28, 2025

Uh oh!

gopherbot commented Oct 28, 2025